Contribution org.nuxeo.ecm.core.automation.core.properties--configuration
In component org.nuxeo.ecm.core.automation.core.properties
org.nuxeo.ecm.core.automation.core.properties
inside nuxeo-automation-core-10.10-HF33-patch-NXP-29565.jar /OSGI-INF/properties-contrib.xml
You can influence this order by adding "require" tags in the containing component declaration, to make sure it is resolved after another component (see "Resolution Order" on components).
This contribution is part of XML component Documentation
This contribution is the default contribution for automation properties.
Here are more details about some of them:
- nuxeo.automation.properties.value.trim: properties are expected to be of the form "key=value". You may wish to trim the potential spaces around value (e.g.: "key = value", will result in "value" and not " value").
- nuxeo.automation.export.aliases: if true, add an operation documentation for each alias of a given operation. Mainly to be backward compatible with old Java Automation client.
- nuxeo.automation.allowVirtualUser: define whether virtual user (non-existent user) is allowed in Nuxeo automation. If allowed, Nuxeo server will not check the user existence during automation execution. Set this property to true if you use Nuxeo computed user or computed group.
@since 8.2
Extension Point
Extension point configuration of component ConfigurationService.Registration Order
6
The registration order represents the order in which this contribution was registered on its target extention
point.
This will impact the override/merge behaviour when it is implemented on the target service, and is useful for
proper customization of existing contributions.
You can influence this order by adding "require" tags in the containing component declaration, to make sure it is resolved after another component (see "Resolution Order" on components).
Contributed Items
XML Source
<extension point="configuration" target="org.nuxeo.runtime.ConfigurationService">
<documentation>
This contribution is the default contribution for automation properties.
Here are more details about some of them:
<ul>
<li>
<strong>nuxeo.automation.properties.value.trim</strong>: properties are expected to be of the form "key=value". You may wish to trim the potential spaces around value (e.g.: "key = value", will result in "value" and not " value").
</li>
<li>
<strong>nuxeo.automation.export.aliases</strong>: if true, add an operation documentation for each alias of a given operation.
Mainly to be backward compatible with old Java Automation client.
</li>
<li>
<strong>nuxeo.automation.allowVirtualUser</strong>: define whether virtual user (non-existent user) is allowed
in Nuxeo automation. If allowed, Nuxeo server will not check the user existence during automation execution.
Set this property to true if you use Nuxeo computed user or computed group.
</li>
</ul>
@since 8.2
</documentation>
<property name="nuxeo.automation.properties.value.trim">false</property>
<property name="nuxeo.automation.export.aliases">false</property>
<property name="nuxeo.automation.allowVirtualUser">false</property>
</extension>